Skip to main content

Google Workspace API Quota Information

info

**If you hit the Google Drive API request limit, SHIELD DRM will automatically retry, so the documents will be processed eventually. There is little for the administrator to do.**However, right after a bulk upload, there may be delays in reflection, and documents that are not processed within 24 hours will stop retrying.

This document is based on the Google Workspace environment. The request limits for the Microsoft 365 environment are 「MS Throttling GuidePlease refer to 」.

What is Google Drive API Quota​

SHIELD DRM retrieves change history through the Google Drive API, processes the downloaded documents, and then uploads them again. Google provides this API for service reliability.Request QuotaI will place it.

  • quota isProject UnitWowUser UnitIt is applied. If requests are concentrated in a short period of time, Google may reject some requests.
  • Rejection response is429 Too Many Requestsor403(rateLimitExceeded · userRateLimitExceeded) is.
  • The limit value is determined by Google and may change. The latest value is in the Google documentUsage limitsPlease refer to.

The Google Cloud project used by SHIELD DRM is operated by the SHIELD DRM service. Customers do not need to apply for or adjust quotas separately.

Response to SHIELD DRM​

Automatic Retry on Exceeding Limit​

If the request hits a limit, SHIELD DRM will perform the corresponding operation.Exponential BackoffI will try again in a different way.

itemAction
Retry TargetQuota exceeded(429, 403Request limit reason), Google server temporary error(5xx)
Retry IntervalStart at 15 seconds and double each time you try, with a maximum of 30 minutes.
Retry StopAfter the initial request24 hoursAfter this, no further retries will be made.
  • If the change history query hits the limit, it will re-query from the last processed point.Detected changes are not omitted.
  • Errors that do not resolve even after retrying, such as insufficient permissions, will not be retried.

Expiration and Re-registration of Change Notification Channel​

The notification channel for changes installed on Drive is according to Google policy.up to 7 daysis valid only during. SHIELD DRM checks the channel every 15 minutes toAutomatically re-register channels with 1 day or less remaining until expirationIt is done. The administrator does not need to reinstall periodically.

Bulk Change Processing​

When many documents are uploaded at once, SHIELD DRM retrieves and processes the change history sequentially. At this time, the reflection of policies may be delayed compared to usual. All changes are processed in order.

Symptoms and Responses Experienced by Administrators​

SymptomsCauseResponse
The decryption of the uploaded document is slower than usual.Exceeded quota or pending processing due to bulk uploadWait without action. It will be handled by automatic restart.
The document has not been processed even after a day.Failed to process after retrying for 24 hours.「Document Conversion LogYou can check the results in "). If you re-upload the document or save it to create new changes, it will be subject to processing again.
Documents on a specific drive are not processed at all.not a quota issueChannel Not InstalledIt is likely to be a permission issue.「Google Drive Event ChannelCheck the channel installation status of the corresponding drive in 」.
The newly created shared drive is not processed.A new shared drive does not automatically install channels.on the admin page동기화Install the rear channel.
Admin Page of the동기화If pressed consecutively, it will be rejected.List synchronization isOnce a minutecan only be executedRe-running in 1 minute.
warning

The most common reason a document is not processed is not the quota but ratherChannel Not InstalledIt is. Before attributing the reflection delay to the quota, please check the channel installation status.

Reference Document​